System and method for automatic application profile and policy creation

ABSTRACT

A system is provided for configuring an application for operation onboard a mobile node that includes a plurality of communication interfaces for accessing a plurality of types of networks. The system includes a network entity that can send a request for an application-specific profile for operating an application onboard the mobile node, the request including information identifying the application. In response, a profile server can create/retrieve an application-specific profile based upon the request. The application-specific profile includes one or more application-specific preferences and/or one or more application-specific settings, where at least one of the application-specific preference(s) and/or setting(s) can be interpreted into one or more policy rules capable of at least partially controlling selection of one or more of the communication interfaces of the mobile node during operation of the application. The application can thereafter be configured at least partially based upon the application-specific profile independent of user input.

BACKGROUND OF THE INVENTION

The mobile Internet Protocol (MIP) enables a mobile terminal to movefreely from one point of connection to another in various networks itvisits along its route. In particular, the MIP protocol describes thoseactions that enable a mobile terminal to maintain connectivity during ahandover from one access router to another access router. For example, amobile terminal operating in an enhanced third-generation (3G) wirelesscommunication network such as 1XEV-DO (TIA/EIA/IS-856) may desire tomove to a wireless local area network (WLAN), and vice versa. In a moreparticular example, consider a terminal user engaged in a voice over IP(VoIP) call in a 1XEV-DO network. When the user enters an area, such asthe user's office, providing WLAN connectivity, the user may desire tomove the VoIP call from the 1XEV-DO network to the WLAN, such as toobtain better or more economical connectivity, speed, quality of service(QoS) and the like.

Contexts such as that described above are generally applicable to mobileterminals that have communication interfaces that permit the mobileterminals to access networks via different interface technologies. Insuch instances, although various networks may be accessible viadifferent interface technologies, in various instances differentaccessible networks differ in their data transmission characteristics,and/or in one or more other dimensions such as their administrativemodels. As will be appreciated, differing data transmissioncharacteristics can impact the kind of applications that can operateover a given interface. And while the data flows of one or moreapplications may be mapped to different network interfaces, such mappingmay require policy decision making within or remote from the respectivemobile terminals.

As the number of communication interfaces and applications increase, theimportance of the mobile terminal as a personal trusted device alsotypically increases. In spite of this increased system complexity,however, it is generally desirable to further simplify the users'interaction with the system, while also providing more personalized andautomated services. In this regard, when downloading and/or installingnew applications to a mobile terminal with multiple interfaces,application profile/settings specific to the respective applications aretypically created to properly operate the applications within theterminal. Currently, terminal users may be required to manuallyconfigure such profile/settings, even though in many instances suchprofile/settings are difficult for users to understand, and thusconfigure.

SUMMARY OF THE INVENTION

In light of the foregoing background, exemplary embodiments of thepresent invention provide an improved system, network entity, profileserver, method and computer program product for configuring anapplication onboard a mobile node that includes a plurality ofcommunication interfaces for accessing a plurality of types of networks.In accordance with exemplary embodiments of the present invention, amobile node (MN) may be configured with one or more base profiles thatinclude base preferences and/or settings interpretable into base policyrules that generally control operation of the mobile node. In variousinstances, the mobile node may download or otherwise receive one or moreapplications for operation thereon. In such instances, before or asthose applications are installed or otherwise initiated for operation,the applications can be automatically configured based uponapplication-specific profiles without user input. Similar to the baseprofiles, the application-specific profiles include preferences and/orsettings, although these preferences and/or settings are specific to therespective applications. Thus, one or more applications installed on themobile node may operate based upon base preferences and/or settingsand/or respective application-specific preferences and/or settingswithout requiring the user to manually configure those applications foroperation.

According to one aspect of the present invention, a system is providedfor configuring an application for operation onboard a mobile node thatincludes a plurality of communication interfaces for accessing aplurality of types of networks. The system includes a network entity,such as the mobile node or an application-provisioning server, and aprofile server located remote from the network entity. The networkentity is capable of sending a request for an application-specificprofile for operating an application onboard the mobile node. Therequest includes information capable of identifying the application suchas, for example, an identifier (ID) associated with the application,and/or one or more characteristics and/or requirements of theapplication.

The profile server is capable of receiving the request, and in responsethereto, creating or otherwise retrieving an application-specificprofile based upon the request. The application-specific profileincludes one or more application-specific preferences and/or one or moreapplication-specific settings, where at least one of theapplication-specific preference(s) and/or setting(s) is capable of beinginterpreted into one or more policy rules capable of at least partiallycontrolling selection of one or more of the communication interfaces ofthe mobile node during operation of the application.

After creating/retrieving the application-specific profile, the profileserver can send the application-specific profile back to the networkentity. Thereafter, the application can be configured at least partiallybased upon the application-specific profile, where the application is atleast partially configured based upon the application-specific profileindependent of user input. In addition, the application may also befurther configured based upon at least one base profile. In this regard,the base profile(s) include one or more base preferences and/or settingsthat are capable of being interpreted into policy rule(s), which inturn, are capable of at least partially controlling operation of themobile node including during operation of the application.

When the network entity comprises a mobile node, the system may furtherinclude an application-provisioning server capable of providing theapplication to the mobile node. In such instances, the mobile node canbe capable of sending the request to the application-provisioningserver, which in turn, is capable of sending a request to the profileserver. Accordingly, the profile server can be capable of receiving therequest from the application-provisioning server, and sending theapplication-specific profile to the application-provisioning server.Upon receiving the application-specific profile, theapplication-provisioning server can then be capable of sending theapplication-specific profile to the mobile node.

According to other aspects of the present invention, a network entity,profile server, method and computer program product are provided forconfiguring an application onboard a mobile node. Exemplary embodimentsof the present invention therefore provide an improved system, networkentity, method and computer program product for configuring anapplication. As indicated above, and explained below, in accordance withexemplary embodiments of the present invention, applications installedor otherwise initiated for operation onboard a mobile node can beautomatically configured for operation from application-specificprofiles. The application-specific profiles, then, can include one ormore preferences and/or settings that are interpretable into policyrules at least partially controlling selection of one or more of thecommunication interfaces of the mobile node during operation of theapplication. Accordingly, the user need not manually configure theapplication for operation, and need not fully understand all of thepreferences and/or settings with which the application is configured. Assuch, the system, network entity, method and computer program product ofexemplary embodiments of the present invention may solve at least someof the problems identified by prior techniques and may provideadditional advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 is a block diagram of one type of mobile node and system thatwould benefit from exemplary embodiments of the present invention;

FIG. 2 is a schematic block diagram of an entity capable of operating asa mobile node, gateway and/or correspondent node, in accordance withexemplary embodiments of the present invention;

FIG. 3 is a schematic block diagram of a mobile node, in accordance withone embodiment of the present invention;

FIG. 4 is an schematic architecture diagram of a number of applicationsoperating on top of a number of services onboard a mobile node, inaccordance with exemplary embodiments of the present invention;

FIG. 5 is a schematic operational block diagram of the system of oneexemplary embodiment of the present invention; and

FIG. 6 is a flowchart illustrating various steps in a method ofconfiguring an application onboard a mobile node, in accordance with oneexemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention now will be described more fully hereinafter withreference to the accompanying drawings, in which exemplary embodimentsof the invention are shown. This invention may, however, be embodied inmany different forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the invention to those skilled in the art. Likenumbers refer to like elements throughout.

Referring to FIG. 1, an illustration of one type of system that wouldbenefit from exemplary embodiments of the present invention is provided.The system, method and computer program product of exemplary embodimentsof the present invention will be primarily described in conjunction withmobile communications applications. It should be understood, however,that the system, method and computer program product of exemplaryembodiments of the present invention can be utilized in conjunction witha variety of other applications, both in the mobile communicationsindustries and outside of the mobile communications industries. Forexample, the system, method and computer program product of exemplaryembodiments of the present invention can be utilized in conjunction withwireline and/or wireless network (e.g., Internet) applications.

As shown, the system can include a mobile node (MN) 10 capable oftransmitting signals to and for receiving signals from base sites orbase stations (BS) 14 (one or more of which may be more particularlyreferred to as access points—APs), two of which are shown in FIG. 1. Asshown and described below, the base stations can include an anchor BS 12a that provides access to one network (e.g., first type of network) anda target BS 12 b that provides access to another network (e.g., secondtype of network) during handoff. One or more base stations are part ofone or more cellular or mobile networks that each include elementsrequired to operate the network, such as a mobile switching center (MSC)(not shown). As well known to those skilled in the art, the mobilenetwork may also be referred to as a Base Station/MSC/Interworkingfunction (BMI). In operation, the MSC is capable of routing calls to andfrom the terminal when the terminal is making and receiving calls. TheMSC can also provide a connection to landline trunks when the terminalis involved in a call. In addition, the MSC can be capable ofcontrolling the forwarding of messages to and from the terminal, and canalso control the forwarding of messages for the terminal to and from amessaging center.

The MN 10 can also be coupled to a data network. For example, one ormore BSs 12 can be coupled to one or more data networks, such as a localarea network (LAN), a metropolitan area network (MAN), and/or a widearea network (WAN). In one typical embodiment, the BS is coupled to agateway (GTW), which is coupled to the data network, such as an InternetProtocol (IP) network 14. The GTWs can comprise any of a number ofdifferent entities capable of providing network connectivity between theMN and other nodes directly or indirectly coupled to the data network.As shown, the GTWs can include a home GTW 16 comprising a router withina home network 20 of the MN, as well as one or more visited GTWscomprising router(s) within one or more visited networks 22 of the MN.As shown, during handoff of the MN from one visited network to another,the GTWs of the respective networks may operate as an anchor GTW 18 acoupled to the anchor BS 12 a and a target GTW 18 b coupled to thetarget BS 12 b. It should be understood, however, that during handofffrom or to the home network, the home GTW may likewise operate as ananchor or target GTW.

As will be appreciated, the GTWs 16, 18 can be described in any of anumber of different manners, such as a home agent (HA), foreign agent(FA), packet data serving node (PDSN), access router (AR) or the like.In this regard, as defined in the MIP (MIP) protocol, a HA comprises arouter within the home network 20 of the MN 10. The HA is capable oftunneling data for delivery to the MN when the MN is away from home, andcan maintain current location information for the MN. A FA, on the otherhand, comprises a router within a visited network 22 of the MN. The FAprovides routing services to the MN while the MN is registered with thevisited network. In operation, the FA detunnels data from the HA, anddelivers the data to the MN. Then, for data sent from a MN registeredwith the visited network, the FA can serve as a default router. Althoughexemplary embodiments of the present invention may be described withreference to a MIP protocol, such as MIPv4 or MIPv6, it should beunderstood that exemplary embodiments of the present invention mayoperate in accordance with any of a number of other protocols.

The other nodes coupled to the MN 10 via the IP network 14 can compriseany of a number of different devices, systems or the like capable ofcommunicating with the MN in accordance with exemplary embodiments ofthe present invention. The other nodes can comprise, for example, GTWsto other networks, personal computers, server computers or the like.Additionally or alternatively, for example, one or more other nodes cancomprise other MNs, such as mobile telephones, portable digitalassistants (PDAs), pagers, laptop computers, or the like. As describedherein, a node capable of communicating with the MN via the IP networkis referred to as a correspondent node (CN) 24, one of which is shown inFIG. 1. It should be understood, however, that in various instances a MNmay be capable of directly communicating with one or more CNs, such asin accordance with any of a number of different short-rangecommunication techniques. For example, a MN may be capable of directlycommunicating with a CN in accordance with radio frequency (RF),Bluetooth (BT), infrared (IrDA), universal serial bus (USB) or any of anumber of different wireline or wireless communication techniques,including LAN techniques, WLAN techniques such as IEEE 802.11, WiMAXtechniques such as IEEE 802.16 or the like.

One or more CNs 24 may be coupled to the IP network via one or moreIntranets 26, one of which is illustrated in FIG. 1. Each Intranetgenerally comprises a private network contained within an enterprise.Each Intranet can comprise one or more interlinked LANs, as well asportions of one or more LANs, MANs, WANs or the like. As with the IPnetwork, CNs can be coupled to the Intranet, and thus the IP network andMN, via the Intranet. Like various other components of the system, theIntranet, and thus the CNs of the Intranet, is typically indirectlycoupled to the IP network, and thus the MN, via a GTW. Similarly,although not shown, each network or portion of a network included withinthe Intranet can be interconnected with one another via a gateway. A MNis capable of accessing the Intranet, and thus CNs of the Intranet, byestablishing a Virtual Private Network (VPN) across a GTW to theIntranet, and if so required, across one or more other gateways withinthe Intranet. In such instances, then, the GTW is typically referred toas a VPN GTW 28, as shown in FIG. 1.

Although not every element of every possible network is shown anddescribed herein, it should be appreciated that the MN 10 can be coupledto one or more of any of a number of different networks. In this regard,mobile network(s) can be capable of supporting communication inaccordance with any one or more of a number of second-generation (2G),2.5G, third-generation (3G) and/or fourth-generation (4G) mobilecommunication protocols or the like. Additionally or alternatively,mobile network(s) can be capable of supporting communication inaccordance with any of a number of different wireless networkingtechniques, including WLAN, WiMAX or the like. Further, for example, themobile network(s) can be capable of supporting communication inaccordance with any one or more of a number of different digitalbroadcast networks, such as Digital Video Broadcasting (DVB) networksincluding DVB-T (DVB-Terrestrial) and/or DVB-H (DVB-Handheld),Integrated Services Digital Broadcasting (ISDB) networks includingISDB-T (ISDB-Terrestrial), or the like.

More particularly, for example, the MN 10 can be coupled to one or morenetworks capable of supporting communication in accordance with 2Gwireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA).Also, for example, one or more of the network(s) can be capable ofsupporting communication in accordance with 2.5G wireless communicationprotocols GPRS, Enhanced Data GSM Environment (EDGE), or the like. Inaddition, for example, one or more of the network(s) can be capable ofsupporting communication in accordance with 3G wireless communicationprotocols such as cdma2000, Universal Mobile Telephone System (UMTS)network employing Wideband Code Division Multiple Access (WCDMA) radioaccess technology. Further, one or more of the network(s) can be capableof supporting enhanced 3G wireless communication protocols such as1XEV-DO (TIA/EIA/IS-856) and 1XEV-DV.

Referring now to FIG. 2, a block diagram of an entity capable ofoperating as a MN 10, GTW 16, 18 and/or CN 24 is shown in accordancewith one embodiment of the present invention. Although shown as separateentities, in some embodiments, one or more entities may support one ormore of a MN, GTW and/or CN, logically separated but co-located withinthe entit(ies). For example, a single entity may support a logicallyseparate, but co-located, GTW and CN.

The entity capable of operating as a MN 10, GTW 16, 18 and/or CN 24includes various means for performing one or more functions inaccordance with exemplary embodiments of the present invention,including those more particularly shown and described herein. It shouldbe understood, however, that one or more of the entities may includealternative means for performing one or more like functions, withoutdeparting from the spirit and scope of the present invention. Moreparticularly, for example, as shown in FIG. 2, the entity can includemeans, such as a processor 30 connected to a memory 32. The memory cancomprise volatile and/or non-volatile memory, and typically storescontent, data or the like. For example, the memory typically storescontent transmitted from, and/or received by, the entity. Also forexample, the memory typically stores client applications, instructionsor the like for the processor to perform steps associated with operationof the entity in accordance with embodiments of the present invention.As explained below, for example, the memory can store clientapplication(s).

As described herein, the client application(s) may each comprisesoftware operated by the respective entities. It should be understood,however, that any one or more of the client applications describedherein can alternatively comprise firmware or hardware, withoutdeparting from the spirit and scope of the present invention. Generally,then, the MN 10, GTW 16, 18 and/or CN 24 can include one or more logicelements for performing various functions of one or more clientapplication(s). As will be appreciated, the logic elements can beembodied in any of a number of different manners. In this regard, thelogic elements performing the functions of one or more clientapplications can be embodied in an integrated circuit assembly includingone or more integrated circuits integral or otherwise in communicationwith a respective network entity (i.e., MN, GTW, CN, etc.) or moreparticularly, for example, a processor 30 of the respective networkentity. The design of integrated circuits is by and large a highlyautomated process. In this regard, complex and powerful software toolsare available for converting a logic level design into a semiconductorcircuit design ready to be etched and formed on a semiconductorsubstrate. These software tools automatically route conductors andlocate components on a semiconductor chip using well established rulesof design as well as huge libraries of pre-stored design modules. Oncethe design for a semiconductor circuit has been completed, the resultantdesign, in a standardized electronic format (e.g., Opus, GDSII, or thelike), may be transmitted to a semiconductor fabrication facility or“fab” for fabrication.

In addition to the memory 32, the processor 30 can also be connected toat least one interface or other means for displaying, transmittingand/or receiving data, content or the like. In this regard, theinterface(s) can include at least one communication interface 34 orother means for transmitting and/or receiving data, content or the like.As explained below, for example, the communication interface(s) caninclude a first communication interface for connecting to a firstnetwork, and a second communication interface for connecting to a secondnetwork. In addition to the communication interface(s), the interface(s)can also include at least one user interface that can include a display35 and/or a user input interface 37. The user input interface, in turn,can comprise any of a number of devices allowing the entity to receivedata from a user, such as a keypad, a touch display, a joystick or otherinput device.

Reference is now made to FIG. 3, which illustrates one type of MN 10that would benefit from exemplary embodiments of the present invention.It should be understood, however, that the MN illustrated andhereinafter described is merely illustrative of one type of MN thatwould benefit from the present invention and, therefore, should not betaken to limit the scope of the present invention. While severalexemplary embodiments of the MN are illustrated and will be hereinafterdescribed for purposes of example, other types of MNs, such as portabledigital assistants (PDAs), pagers, laptop computers and other types ofelectronic systems, can readily employ exemplary embodiments of thepresent invention.

The MN 10 includes various means for performing one or more functions inaccordance with exemplary embodiments of the present invention,including those more particularly shown and described herein. It shouldbe understood, however, that the MN may include alternative means forperforming one or more like functions, without departing from the spiritand scope of the present invention. More particularly, for example, asshown in FIG. 3, in addition to an antenna 36, the MN 10 can include atransmitter 38, receiver 40, and means, such as a controller 42 or otherprocessor, that provides signals to and receives signals from thetransmitter and receiver, respectively. These signals include signalinginformation in accordance with the air interface standard of theapplicable cellular system, and also user speech and/or user generateddata. In this regard, the MN can be capable of operating with one ormore air interface standards, communication protocols, modulation types,and access types. More particularly, the MN can be capable of operatingin accordance with any of a number of second generation (2G), 2.5Gand/or third-generation (3G) communication protocols or the like. Forexample, the MN may be capable of operating in accordance with 2Gwireless communication protocols IS-136 (TDMA), GSM and IS-95 (CDMA),2.5G wireless communication protocols such as GPRS and/or Enhanced DataGSM Environment (EDGE), and/or 3G wireless communication protocols suchas cdma2000, Universal Mobile Telephone System (UMTS) network employingWideband Code Division Multiple Access (WCDMA) radio access technology.Also, for example, the MN can also be capable of operating in accordancewith enhanced 3G wireless communication protocols such as 1XEV-DO(TIA/EIA/IS-856) and 1XEV-DV.

It is understood that the controller 42 includes the circuitry requiredfor implementing the audio and logic functions of the MN 10. Forexample, the controller may be comprised of a digital signal processordevice, a microprocessor device, and various analog-to-digitalconverters, digital-to-analog converters, and other support circuits.The control and signal processing functions of the MN are allocatedbetween these devices according to their respective capabilities. Thecontroller can additionally include an internal voice coder (VC) 42 a,and may include an internal data modem (DM) 42 b. Further, thecontroller may include the functionality to operate one or more softwareprograms, which may be stored in memory (described below). For example,the controller may be capable of operating a connectivity program, suchas a conventional Web browser. The connectivity program may then allowthe MN to transmit and receive Web content, such as according to HTTPand/or the Wireless Application Protocol (WAP), for example.

The MN 10 also comprises a user interface including a conventionalearphone or speaker 44, a ringer 46, a microphone 48, a display 50, anda user input interface, all of which are coupled to the controller 42.The user input interface, which allows the MN to receive data, cancomprise any of a number of devices allowing the MN to receive data,such as a keypad 52, a touch display (not shown) or other input device.In embodiments including a keypad, the keypad includes the conventionalnumeric (0-9) and related keys (#, *), and other keys used for operatingthe MN. Although not shown, the MN can include a battery, such as avibrating battery pack, for powering the various circuits that arerequired to operate the MN, as well as optionally providing mechanicalvibration as a detectable output.

The MN 10 can also include one or more means for sharing and/orobtaining data. For example, the MN can include a short-range radiofrequency (RF) interface 54 so that data can be shared with and/orobtained from electronic devices in accordance with RF techniques. Inthis regard, the RF interface may function as a WLAN and/or WANinterface capable of sharing data with other radio frequency interfacesin accordance with WLAN and/or WAN techniques. More particularly, forexample, the RF interface may function as a WLAN interface, or the MNmay include a separate WLAN interface 55, capable of sharing data inaccordance with WLAN techniques such as IEEE 802.11, WiMAX techniquessuch as IEEE 802.16 or the like. Similarly, for example, the MN caninclude a separate WAN interface 57 capable of sharing data inaccordance with WAN techniques. The MN can additionally or alternativelyinclude other wireline and/or wireless interfaces. For example, the MNcan include a universal serial bus (USB) interface 59, and/orshort-range wireless interfaces, such as an infrared (IR) interface 56,and/or a Bluetooth (BT) interface 58 operating using Bluetooth brandwireless technology developed by the Bluetooth Special Interest Group.The MN can therefore additionally or alternatively be capable oftransmitting data to and/or receiving data from electronic devices inaccordance with such techniques.

The MN 10 can further include memory, such as a subscriber identitymodule (SIM) 60, a removable user identity module (R-UIM) or the like,which typically stores information elements related to a mobilesubscriber. In addition to the SIM, the MN can include other removableand/or fixed memory. In this regard, the MN can include volatile memory62, such as volatile Random Access Memory (RAM) including a cache areafor the temporary storage of data. The MN can also include othernon-volatile memory 64, which can be embedded and/or may be removable.The non-volatile memory can additionally or alternatively comprise anEEPROM, flash memory or the like. The memories can store any of a numberof software applications, instructions, pieces of information, and data,used by the MN to implement the functions of the MN. For example, thememories can store an identifier, such as an international mobileequipment identification (IMEI) code, international mobile subscriberidentification (IMSI) code, mobile station integrated services digitalnetwork (MSISDN) code (mobile telephone number), Internet Protocol (IP)address, Session Initiation Protocol (SIP) address or the like, capableof uniquely identifying the MN.

A number of network entities of the-system (e.g., MN 10, CN 24, etc.)are configured to operate in accordance with a protocol stack, such asthe protocol stack provided by the Open Systems Interconnection (OSI)model. As will be appreciated, the protocol stack may be implemented insoftware, hardware, firmware or combinations of the same. Moreparticularly, the OSI model comprises seven layers, including anapplication layer, presentation layer, session layer, transport layer,network layer, data link layer and physical layer. The OSI model wasdeveloped by the International Organization for Standardization (ISO)and is described in ISO 7498, entitled: The OSI Reference Model, thecontents of which are incorporated herein by reference in its entirety.Generally, each layer of the OSI model performs a specific datacommunications task, a service to and for the layer that precedes it(e.g., the network layer provides a service for the transport layer).The process can be likened to placing a letter in a series of envelopesbefore it is sent through the postal system. Each succeeding envelopeadds another layer of processing or overhead information necessary toprocess the transaction. Together, all the envelopes help make sure theletter gets to the right address and that the message received isidentical to the message sent. Once the entire package is received atits destination, the envelopes are opened one by one until the letteritself emerges exactly as written.

Actual data flow between two entities (e.g., MN 10 and CN 24) is fromtop to bottom in the source entity, across the communications line, andthen from bottom to top in the destination entity. Each time that userapplication data passes downward from one layer to the next layer in thesame entity more processing information is added. When that informationis removed and processed by the peer layer in the other entity, itcauses various tasks (error correction, flow control, etc.) to beperformed.

As explained in the background section, as the number of communicationinterfaces and applications of a MN 10 increase, the importance of theMN as a personal trusted device also typically increases. In spite ofthis increased system complexity, however, it is generally desirable tofurther simplify the users' interaction with the system, while alsoproviding more personalized and automated services. In this regard, whendownloading and/or installing new applications to a MN with multipleinterfaces, application profile/settings specific to the respectiveapplications are typically created to properly operate the applicationswithin the terminal. Currently, MN users may be required to manuallyconfigure such profile/settings, even though in many instances suchprofile/settings are difficult for users to understand, and thusconfigure.

Therefore, in accordance with exemplary embodiments of the presentinvention, a MN 10 may be configured with one or more base profiles thatinclude one or more base preferences (parameters that guide operation ofthe MN) and/or settings (parameters that restrict operation of the MN).The base preferences and/or settings can then be interpreted into one ormore base policy rules that generally control operation of the MN. Whenvarious applications are installed or otherwise initiated on the MN,however, those applications can be automatically configured based uponapplication-specific profiles without user input, where theapplication-specific profiles include one or more preferences and/orsettings specific to the respective applications. Theapplication-specific preferences and/or settings can likewise beinterpreted into one or more application-specific policy rules thatcontrol operation of the respective application, and thus the MN duringoperation of the respective application. In such instances, one or moreof the application-specific preferences and/or settings may supersedeone or more conflicting base preferences and/or settings duringoperation of the respective applications. Accordingly, applicationsinstalled on the MN may operate based upon base preferences and/orsettings and/or respective application-specific preferences and/orsettings.

As will be appreciated, application-specific profiles including one ormore application-specific preferences and/or settings can be generatedor otherwise provided in any of a number of different manners. Asexplained below, for example, one or more applications may be associatedwith one or more application identifiers. The application identifier(s),in turn, may be associated with one or more application-specificpreferences and/or settings, and/or one or more application-specificprofiles including one or more such parameters and/or settings. At someinstance before or during installation or initiation of an application,application-specific preferences/settings and/or profile(s) can beretrieved based upon respective application identifier(s). Anapplication-specific profile can then be generated or otherwise providedbased upon the retrieved application-specific preferences/settingsand/or profile(s).

Reference is now made to FIG. 4, which illustrates an architecturediagram of a number of applications 66 (e.g., application 1, application2, etc.) operating on top of a number of services 68 (e.g., service A,service B, service C, service D, etc.) onboard a MN 10 in accordancewith exemplary embodiments of the present invention. As shown, theapplications can comprise any of a number of different softwareapplications including, for example, a WAP (Wireless ApplicationProtocol) browser, file (e.g, MP3) transfer client, messaging (e.g.,MMS, SMS, email, etc.) client, short-range connectivity OBEX (ObjectExchange) engine, PC-connectivity, Bluetooth and IR stacks, PIM(personal information management) and/or telephony applications.Likewise, the services can comprise any of a number of differentservices accessible to the MN user via one or more applications. Forexample, the services can include IP browsing, IP real-time, IPbackground, messaging, telephony, video conferencing and/or VPNtunneling. In various instances the MN includes a number of differentcommunication interfaces for accessing a number of different types ofnetworks (e.g., WLAN, GPRS, VPN, etc.). In such instances, one or moreof the services can be configured to communicate with one or moreparticular communication interfaces of the MN for accessing one or moreparticular types of networks to effectuate the respective services. Inturn, one or more of the applications can be configured to communicatewith one or more particular services for operating the respectiveapplication(s) via the respective service(s).

As also shown in FIG. 4, the MN 10 may be configured with one or morebase profiles 70 that include one or more base preferences (parametersthat guide operation of the MN) and/or settings (parameters thatrestrict operation of the MN). As shown, the base profiles can include adefault profile as well as a best service profile and a customizedprofile. Although not shown, other examples of base profiles includeuser profiles, such as for silent operation or operation when the useris in a meeting, and/or “presence” profiles, such as for operation atwork and/or at home. These base preferences and/or settings can then beinterpreted into one or more base policy rules that generally controloperation of the MN, such as during effectuation of a particular service68. In addition, one or more of the applications 66 operating onboardthe MN may be configured with application-specific profiles 72 includingone or more preferences and/or settings specific to the respectiveapplications, where these application-specific preferences and/orsettings may also be interpreted into one or more application-specificpolicy rules that control operation of the respective application, suchas during operation of the respective application(s) via particularservices. As indicated above, then, one or more of theapplication-specific preferences and/or settings may supersede one ormore conflicting base preferences and/or settings during operation ofthe respective applications.

As shown and described herein, the profiles can include any of a numberof different base/application-specific preferences and/or settings uponwhich the MN 10 generally, and/or applications of the MN 10 moreparticularly, operate, such as to select the communication interface andthus the type of network that the MN/applications access duringoperation. For example, the one or more profiles can include preferencesand/or settings related to price (e.g., cheapest price) where the costto access different types of networks may be the dominating factor, orcapacity (e.g., highest capacity) where quality of service (QoS)available in accessing different types of networks may be the dominatingfactor. Also, for example, one or more profiles can include preferencesand/or settings related to services and/or availability (e.g., bestservices and/or availability) where network connectivity and/or serviceavailability may be the dominating factors, and/or battery power whereuptime (e.g., highest uptime) of the MN may be the dominating factor.Additionally or alternatively, for example, one or more profiles caninclude preferences and/or settings related to a level of control overthe device for security purposes (maintenance and/or surveillance),service redirection, and/or customization of services for groups of MNusers (e.g., employees of a company). Further, for example, one or moreprofiles can include preferences and/or settings related to control overservices that a MN user accesses, roaming decisions or the like. As willbe appreciated, the profiles can comprise any of a number of differentpreferences and/or settings from a number of different sourcesincluding, for example, MN users, information technology (IT)departments, network operators, service providers, or the like.

Reference is now made to FIGS. 5 and 6, which illustrate an operationalblock diagram of a system and a flowchart of various steps in a methodof configuring an application 66 in accordance with exemplaryembodiments of the present invention. As shown in FIG. 5, to effectuateconfiguring an application, a MN 10 can communicate with a number ofCNs, including an application provisioning server 26 a, a profile server26 b and/or an authentication server 26 c, via a number of differentcommunication channels. More particularly, for example, MN cancommunicate with the application provisioning server across acommunication channel A. The application provisioning server, in turn,can communicate with the profile server across channel B, and theprofile server can communicate with the authentication server acrosschannel C. Also, for example, the MN can communicate with the profileserver across channel D, which may or may not pass through theapplication provisioning server therebetween. Further, for example, theMN can communicate with the authentication server across channel E.Similar to above, although shown as separate entities, in someembodiments, one or more entities may support one or more of a MN,application provisioning server, profile server and/or authenticationserver, logically separated but co-located within the entit(ies). Forexample, a single entity may support a logically separate, butco-located, application provisioning server and profile server, profileserver and authentication server, or application provisioning server,profile server and authentication server. Additionally or alternatively,a single entity may support a logically separate, but co-located, MN andprofile server, MN and authentication server, or MN, profile server andauthentication server.

In accordance with one exemplary embodiment of the present invention,configuring an application 66 for operation onboard a MN 10 includesreceiving or otherwise downloading an application at the MN, as shown inblock 80. The application can be received or otherwise downloaded fromany of a number of different sources in any of a number of differentmanners. In one embodiment, for example, the MN downloads theapplication from an application provisioning server 26 a acrosscommunication channel A. At some point as or after the MN receives theapplication, the application is initiated or otherwise installed onboardthe MN, as shown in block 82. In this regard, as the application isinitiated/installed, the MN can determine if the application has anassociated application profile identifier (ID), as shown in block 84. Ifthe application does not have an associated application profile ID, theMN can proceed in a number of different manners. For example, the MN canproceed to initiate/install the MN by configuring the application basedupon one or more base profiles 70, as shown in block 86. In this regard,if the MN includes one base profile, the MN can configure theapplication based upon that profile. If the MN includes more than onebase profile, however, the MN can select a base profile or receive aselection of a base profile, and/or select one or more preferencesand/or settings from more than one base profile and/or receive aselection of one or more preferences and/or settings from more than onebase profile.

If the application 66 does have an associated application profile ID,the MN 10 can proceed to initiate/install the MN by configuring theapplication based upon one or more application-specific profile(s) 72 atleast one of which is capable of being identified based upon therespective ID. In this regard, configuring the application based uponapplication-specific profile(s) can include communicating with anapplication provisioning server 26 a, which may be the same or differentfrom the server that provided the application to the MN, as shown inblock 88. The application provisioning server can be selected in any oneof a number of different ways. For example, the application provisioningserver can be selected by pre-configuring the application to direct theMN to receive application-specific profile(s) for the respectiveapplication from one of one or more particular application provisioningservers.

During communication with the application provisioning server 26 a, theMN 10 can request application-specific profile(s) 72 for the respectiveapplication 66, where the request can include the application profile IDand may include one or more other pieces of information. For example,the profile request can also include an ID of a policy server 26 bproviding policy services to the MN, if so desired or otherwiserequired. Additionally or alternatively, for example, the profilerequest can also include ID(s) associated with the MN and/or MN user,and/or one or more pieces of information related to capabilities of theMN (e.g., included communication interfaces, etc.). Upon receipt of theprofile request, the application provisioning server can initiatecommunication with a profile server 26 b across channel B to retrieveapplication-specific profile(s) for the respective application, such asbased upon a profile server ID, as shown in block 90. As the applicationprovisioning server initiates communication with the profile server, theprofile server may require authentication of the applicationprovisioning server, such as in any of a number of different manners, asshown in block 92. For example, the profile server can authenticate theapplication provisioning server in accordance with the genericauthentication architecture (GAA).

Presuming the profile server 26 b successfully authenticates theapplication provisioning server 26 a, the application provisioningserver can request application-specific profile(s) 72 based upon theapplication profile ID and, if so desired or otherwise necessary, one ormore other pieces of information such as, for example, ID(s) associatedwith the MN 10 and/or MN user, and/or one or more pieces of informationrelated to capabilities of the MN (e.g., included communicationinterfaces, etc.), as shown in block 94. Upon receipt of the requestfrom the application provisioning server, the profile server mayadditionally require authentication of the MN and/or MN user, such as inany of a number of different manners, as shown in block 96. For example,the profile server can authenticate the MN and/or MN user bycommunicating with the MN across channel D, such as in accordance withGAA. To authenticate the MN and/or MN user, the profile server maycommunicate with an authentication server 26 c across channel C. In suchinstances, the MN and/or MN user may have a predefined securityassociation (SA), previously established across channel E.

In response to the request from the application provisioning server 26a, and presuming the MN 10 and/or MN user is authenticated (ifrequired), the profile server 26 b can retrieve or otherwise createapplication-specific profile(s) 72 based upon the request, such as inany of a number of different manners, as shown in block 98. For example,the profile server can retrieve application-specific profile(s) basedupon the application profile ID in the request, such as from a databaseof application-specific profile(s) maintained by the profile server.Alternatively, the profile server can create application-specificprofile(s) based upon the application profile ID in the request, such asfrom a database of application-specific parameters and/or settingsmaintained by the profile server. Additionally or alternatively, forexample, the profile server can retrieve or otherwise createapplication-specific profile(s) based upon the MN and/or MN user, assuch may be identifiable from the MN and/or MN user ID(s), and/orinformation related to the capabilities of the MN. More particularly,for example, the profile server can retrieve application-specificprofile(s) based upon the application profile ID and further based uponthe MN, MN user and/or MN capability information, such as from thedatabase of application-specific profile(s). Alternatively, the profileserver can create application-specific profile(s) based upon theapplication profile ID and further based upon the MN, MN user and/or MNcapability information, such as from the database ofapplication-specific parameters and/or settings.

When the profile server 26 b retrieves or otherwise createsapplication-specific profile(s) 72 based upon the MN and/or MN user, thedatabase of application-specific profile(s) and/or the database ofapplication-specific parameter and/or settings may include profile(s)and/or preference(s)/setting(s), respectively, associated with therespective MN ID and/or MN user ID. Those profile(s) and/orpreference(s)/setting(s) may be previously specified by the user andstored in the respective database(s), such as during previouscommunication with the profile server. In addition to storing profile(s)and/or preference(s)/setting(s) associated with the MN ID and/or MN userID, the profile server may store MN capability information associatedwith the MN ID and/or MN user ID. In such instances, the request to theapplication provisioning server 26 a, and thus the profile server, neednot include such capability information.

Irrespective of how the profile server 26 b retrieves/createsapplication-specific profile(s) 72 for the application 66 beinginitiated/installed by the MN 10, the application-specific profile(s)can thereafter be provided to the MN, as shown in block 100. Forexample, profile server can thereafter transfer the application-specificprofile(s) to the application provisioning server 26 a in response tothe request from the application provisioning server. In turn, theapplication provisioning server can transfer the application-specificprofile(s) to the MN in response to the previous profile request fromthe MN. Upon receipt of the application-specific profile(s), the MN canproceed to initiate/install the MN by configuring the application basedupon the application-specific profile(s), as shown in block 102. Inaddition, as one or more configurable preferences and/or settings of theapplication may not be specified by the application-specific profile(s),the application may be further configured based upon one or more baseprofiles 70, such as to configure the unspecified preferences and/orsettings of the application, as shown in block 104.

As explained above, the MN 10 receives or otherwise downloads anapplication 66, and when the application has an associated applicationprofile ID, requests and thereafter receives application-specificprofile(s) 72 for that application from an application provisioningserver 26 a (receiving the profile(s) from a profile server 26 b). TheMN can then configure the received/downloaded application based upon theapplication-specific profile(s). It should be understood, however, thatthe application can be configured with such application-specificprofile(s) in any of a number of other manners. For example, in lieu ofreceiving the application and then receiving the application-specificprofile(s) to configure the application, the MN can request theapplication from the application provisioning server. In response to theapplication request, the application provisioning server itself canrequest/receive application-specific profile(s), such as in the samemanner explained above with respect to the MN requesting/receiving suchprofiles via the application provisioning server. Upon receiving theapplication-specific profile(s), the application provisioning server canconfigure the application, such as in the same manner as the MN, andthereafter transmit the configured application to the MN. Uponinitiating/installing the application, then, the MN need not configurethe application based upon the application-specific profile(s). Anddepending upon whether the application provisioning server furtherconfigures unspecified preferences and/or settings of the applicationbased upon one or more base profiles 70, the MN may or may not need tofurther configure the application in this manner.

It should also be understood that the profile server 26 b can at leastpartially retrieve or otherwise create application-specific profile(s)72 without or independent of an application profile ID. In suchinstances, in addition to or lieu of an application profile ID, therequest to the profile server can include one or more characteristics,requirements or the like of the respective application 66. For example,the request can identify a class or type of the application, such as abrowsing application, file transfer application or the like.Additionally or alternatively, the request can identify QoSrequirements, security requirements or the like of the application. Inresponse to such a request, then, the profile server can retrieve orotherwise create application-specific profile(s) additionally oralternatively based upon such characteristics, requirements or the like.Generally, then, the request to the profile server can includeinformation capable of at least partially identifying an application,where the information can include an application profile ID, and/orcharacteristics, requirements or the like of the application.

It should further be understood that the profile server 26 b mayretrieve or otherwise create application-specific profile(s) 72 for anapplication 66 in an incremental manner based upon multiple requests,and/or the MN 10 or application provisioning server 26 a mayincrementally configure the application based upon retrieved/createdapplication-specific profile(s). In such instances, the profile servermay receive multiple requests for application-specific profile(s), orfor preference(s) and/or setting(s) of application-specific profile(s).And although the profile server may authenticate theapplication-provisioning server, MN and/or MN user for each request, theprofile server may more typically authenticate theapplication-provisioning server, MN and/or MN user for the first requestand maintain that authentication for each subsequent request withrespect to the same application-provisioning server, MN, MN user and/orapplication.

Moreover, although one or more of the application-specific preferencesand/or settings may supersede one or more conflicting base preferencesand/or settings during operation of the respective applications, one ormore base preferences and/or settings may be predefined as incapable ofbeing superseded or as otherwise having a higher priority. In suchinstances, although an application-specific preference and/or settingmay conflict with a corresponding predefined preference and/or setting,the application can be configured based upon the respective basepreference and/or setting in lieu of the otherwise supersedingapplication-specific preference and/or setting. Alternatively, the MN 10may solicit, and thereafter receive, user input selecting to configurethe application based upon the respective base preference and/orsetting, or the otherwise superseding application-specific preferenceand/or setting.

Further, it should be understood that although the profile server 26 bis capable of providing application-specific profile(s) includingapplication-specific preferences and/or settings, the profile server mayalso be capable of providing other preferences and/or settings for atleast partially controlling operation of the MN 10 and/or application66. For example, the profile server may be capable of providing the MNwith one or more base profile(s), and/or one or more base preferencesand/or base settings. More particularly, for example, the profile servermay be capable of providing the MN with addressing information such asan email address, home network IP address, telephone number or the like,and/or operation information such as country details, subscriptiondetails or the like.

Irrespective of exactly how an application 66 is configured, afterinitiating/installing the application, the application may thereafter beoperated onboard the MN 10 at least partially based upon theapplication-specific/base profile(s) with which the application isconfigured. In this regard, before or as the application is operated,the MN can interpret the preferences and/or settings of the configuredapplication-specific/base profile(s) into one or moreapplication-specific policy rules that may be implemented by a policymanager (e.g., software application, firmware and/or hardware) tocontrol operation of the respective application, and thus the MN duringoperation of the respective application. More particularly, for example,after configuring the application, the respective preferences and/orsettings can be interpreted into application-specific policy rule(s)that are thereafter stored in a policy database maintained by the MN,such as in non-volatile memory (e.g., memory 32, 64). At one or moreinstances during operation of the application, then, the policy managercan receive a use case from the application describing one or moreconditions under which the application is operating, or desires tooperate. The policy manager can then process the use case based uponpolicy rule(s) in the policy database such that the policy manager candirect or otherwise control operation of the of the applicationconsistent with the respective policy rule(s).

The policy rules controlling operation of the application 66, and thusthe MN 10 during operation of the application, can comprise any of anumber of different rules effectuating the configured preferences and/orsettings. For example, consider instances in which the MN includes anumber of different communication interfaces for accessing a number ofdifferent types of networks (e.g., WLAN, GPRS, VPN, etc.). In suchinstances, one or more policy rules may control the service(s) withwhich the application communicates to access the respective service(s),and/or the communication interface(s) with which the respectiveservice(s) communicate to access respective type(s) of network(s), toeffectuate operation of the application. In this regard, thecommunication interface(s) over which the applications communicate (viarespective service(s)), and thus the types of network(s) accessed, suchas during network connection, handoff or the like, can be selectivelycontrolled at least partially based upon the policy rule(s) into whichthe configured preferences and/or settings are interpreted.

Consider, for example, interpreting preferences and/or settingsconfigured for a data backup application (i.e., application 66) into oneor more policy rules, where the data backup application communicatesacross a network during operation to backup data to a remote storageentity. In such an instance, a policy rule may specify that theapplication only operates with communication to a WLAN, and accordinglyonly communicates with a service 68 that communicates with a WLANinterface (i.e., communication interface) of the MN 10 to provide accessto a WLAN when such a network is available. In another example, considerinterpreting preferences and/or settings configured for a media (e.g.,MP3 music) downloading application into one or more policy rules. Inthis instance, a policy rule may specify that the application onlydownload new media over the least costly available network, and/or onlydownload new media when the network is the least congested, such as atnight.

According to one exemplary aspect of the present invention, thefunctions performed by one or more of the entities of the system, suchas the MN 10, application provisioning server 26 a, profile server 26 band/or authentication server 26 c, may be performed by various means,such as hardware and/or firmware, including those described above, aloneand/or under control of a computer program product. The computer programproduct for performing one or more functions of exemplary embodiments ofthe present invention includes a computer-readable storage medium, suchas the non-volatile storage medium, and software includingcomputer-readable program code portions, such as a series of computerinstructions, embodied in the computer-readable storage medium.

In this regard, FIG. 6 is a flowchart of systems, methods and programproducts according to exemplary embodiments of the present invention. Itwill be understood that each block or step of the flowchart, andcombinations of blocks in the flowchart, can be implemented by variousmeans, such as hardware, firmware, and/or software including one or morecomputer program instructions. As will be appreciated, any such computerprogram instructions may be loaded onto a computer or other programmableapparatus (i.e., hardware) to produce a machine, such that theinstructions which execute on the computer or other programmableapparatus create means for implementing the functions specified in theflowchart block(s) or step(s). These computer program instructions mayalso be stored in a computer-readable memory that can direct a computeror other programmable apparatus to function in a particular manner, suchthat the instructions stored in the computer-readable memory produce anarticle of manufacture including instruction means which implement thefunction specified in the flowchart block(s) or step(s). The computerprogram instructions may also be loaded onto a computer or otherprogrammable apparatus to cause a series of operational steps to beperformed on the computer or other programmable apparatus to produce acomputer-implemented process such that the instructions which execute onthe computer or other programmable apparatus provide steps forimplementing the functions specified in the flowchart block(s) orstep(s).

Accordingly, blocks or steps of the flowchart support combinations ofmeans for performing the specified functions, combinations of steps forperforming the specified functions and program instruction means forperforming the specified functions. It will also be understood that oneor more blocks or steps of the flowchart, and combinations of blocks orsteps in the flowchart, can be implemented by special purposehardware-based computer systems which perform the specified functions orsteps, or combinations of special purpose hardware and computerinstructions.

Many modifications and other exemplary embodiments of the invention willcome to mind to one skilled in the art to which this invention pertainshaving the benefit of the teachings presented in the foregoingdescriptions and the associated drawings. Therefore, it is to beunderstood that the invention is not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

1. A system for configuring an application for operation onboard amobile node including a plurality of communication interfaces foraccessing a plurality of types of networks, the system comprising: anetwork entity configured to send a request for an application-specificprofile for operating an application onboard a mobile node, the requestincluding information identifying the application; and a profile serverlocated remote from the network entity, wherein the profile server isconfigured to receive the request, and in response thereto, one ofcreate or retrieve an application-specific profile based upon therequest, and send the application-specific profile to the networkentity, wherein the application-specific profile includes at least oneof at least one application-specific preference or at least oneapplication-specific setting, wherein at least one of the at least oneapplication-specific preference or at least one application-specificsetting are interpretable into at least one policy rule for at leastpartially controlling selection of at least one of the communicationinterfaces of the mobile node during operation of the application, andwherein the profile server is configured to send theapplication-specific profile such that the application is thereafterconfigurable at least partially based upon the application-specificprofile, the application being at least partially configured based uponthe application-specific profile independent of user input.
 2. A systemaccording to claim 1, wherein the network entity is configured to send arequest including an identifier associated with the application, andwherein the profile server is configured to one of create or retrievethe application-specific profile at least partially based upon theidentifier.
 3. A system according to claim 1, wherein the network entityis configured to send a request including at least one of at least onecharacteristic or at least one requirement of the application, andwherein the profile server is configured to one of create or retrievethe application-specific profile at least partially based upon the atleast one of the at least one characteristic or the at least onerequirement of the application.
 4. A system according to claim 1,wherein the profile server is configured to send theapplication-specific profile such that the application is thereafterconfigurable further based upon at least one base profile, wherein theat least one base profile includes at least one of at least one basepreference or at least one base setting, wherein at least one of the atleast one base preference or at least one base setting are interpretableinto at least one policy rule for at least partially controllingoperation of the mobile node including during operation of theapplication.
 5. A system according to claim 1, wherein the networkentity comprises the mobile node, and wherein the system furthercomprises: an application-provisioning server configured to provide theapplication to the mobile node, wherein the mobile node is configured tosend the request to the application-provisioning server, which in turn,is configured to send a request to the profile server, wherein theprofile server is configured to receive the request from theapplication-provisioning server, and send the application-specificprofile to the application-provisioning server, which in turn, isconfigured to send the application-specific profile to the mobile node.6. A network entity for configuring an application for operation onboarda mobile node including a plurality of communication interfaces foraccessing a plurality of types of networks, the network entitycomprising: a processing element configured to send a request for anapplication-specific profile for operating an application onboard amobile node, the request including information identifying theapplication, wherein the processing element configured to receive anapplication-specific profile in response to the request, theapplication-specific profile having been one of created or retrievedbased upon the request, wherein the application-specific profileincludes at least one of at least one application-specific preference orat least one application-specific setting, wherein at least one of theat least one application-specific preference or at least oneapplication-specific setting are interpretable into at least one policyrule for at least partially controlling selection of at least one of thecommunication interfaces of the mobile node during operation of theapplication, and wherein the processing element is configured to receivethe application-specific profile such that the application is thereafterconfigurable at least partially based upon the application-specificprofile, the application being at least partially configured based uponthe application-specific profile independent of user input.
 7. A networkentity according to claim 6, wherein the processing element isconfigured to send a request including an identifier associated with theapplication, and wherein the processing element is configured to receivean application-specific profile having been one of created or retrievedat least partially based upon the identifier.
 8. A network entityaccording to claim 6, wherein the processing element is configured tosend a request including at least one of at least one characteristic orat least one requirement of the application, and wherein the processingelement is configured to receive an application-specific profile havingbeen one of created or retrieved at least partially based upon the atleast one of the at least one characteristic or the at least onerequirement of the application.
 9. A network entity according to claim6, wherein the processing element is configured to send a request fromthe mobile node to a profile server located remote from the mobile node,and wherein the processing element is configured to receive anapplication-specific profile at the mobile node from the profile serverin response to the request.
 10. A network entity according to claim 6,wherein the processing element is configured to receive theapplication-specific profile such that the application is thereafterconfigurable further based upon at least one base profile, wherein theat least one base profile includes at least one of at least one basepreference or at least one base setting, wherein at least one of the atleast one base preference or at least one base setting are interpretableinto at least one policy rule for at least partially controllingoperation of the mobile node including during operation of theapplication.
 11. A profile server for configuring an application foroperation onboard a mobile node including a plurality of communicationinterfaces for accessing a plurality of types of networks, the profileserver comprising: a processing element configured to receive, from anetwork entity, a request for an application-specific profile foroperating an application onboard a mobile node, the request includinginformation identifying the application, wherein the processing elementis configured to respond to the request by one of creating or retrievingan application-specific profile based upon the request, and send theapplication-specific profile to the network entity, wherein theapplication-specific profile includes at least one of at least oneapplication-specific preference or at least one application-specificsetting, wherein at least one of the at least one application-specificpreference or at least one application-specific setting areinterpretable into at least one policy rule for at least partiallycontrolling selection of at least one of the communication interfaces ofthe mobile node during operation of the application, and wherein theprocessing element is configured to send the application-specificprofile such that the application is thereafter configurable at leastpartially based upon the application-specific profile, the applicationbeing at least partially configured based upon the application-specificprofile independent of user input.
 12. A profile server according toclaim 11, wherein the processing element is configured to receive arequest including an identifier associated with the application, andwherein the processing element is configured to one of create orretrieve the application-specific profile at least partially based uponthe identifier.
 13. A profile server according to claim 11, wherein theprocessing element is configured to receive a request including at leastone of at least one characteristic or at least one requirement of theapplication, and wherein the processing element is configured to one ofcreate or retrieve the application-specific profile at least partiallybased upon the at least one of the at least one characteristic or the atleast one requirement of the application.
 14. A profile server accordingto claim 11, wherein the processing element is configured to send theapplication-specific profile such that the application is thereafterconfigurable further based upon at least one base profile, wherein theat least one base profile includes at least one of at least one basepreference or at least one base setting, wherein at least one of the atleast one base preference or at least one base setting are interpretableinto at least one policy rule for at least partially controllingoperation of the mobile node including during operation of theapplication.
 15. A method of configuring an application for operationonboard a mobile node including a plurality of communication interfacesfor accessing a plurality of types of networks, the method comprising:sending a request for an application-specific profile for operating anapplication onboard a mobile node, the request including informationidentifying the application; and receiving an application-specificprofile in response to the request, the application-specific profilehaving been one of created or retrieved based upon the request, whereinthe application-specific profile includes at least one of at least oneapplication-specific preference or at least one application-specificsetting, wherein at least one of the at least one application-specificpreference or at least one application-specific setting areinterpretable into at least one policy rule for at least partiallycontrolling selection of at least one of the communication interfaces ofthe mobile node during operation of the application, and wherein theapplication-specific profile is received such that the application isthereafter configurable at least partially based upon theapplication-specific profile, the application being at least partiallyconfigured based upon the application-specific profile independent ofuser input.
 16. A method according to claim 15, wherein the sending stepcomprises sending a request including an identifier associated with theapplication, and wherein the receiving step comprises receiving anapplication-specific profile having been one of created or retrieved atleast partially based upon the identifier.
 17. A method according toclaim 15, wherein the sending step comprises sending a request includingat least one of at least one characteristic or at least one requirementof the application, and wherein the receiving step comprises receivingan application-specific profile having been one of created or retrievedat least partially based upon the at least one of the at least onecharacteristic or the at least one requirement of the application.
 18. Amethod according to claim 15, wherein the sending step comprises sendinga request from the mobile node to a profile server located remote fromthe mobile node, and wherein the receiving step comprises receiving anapplication-specific profile at the mobile node from the profile serverin response to the request.
 19. A method according to claim 15, whereinthe application-specific profile is received such that the applicationis thereafter configurable further based upon at least one base profile,wherein the at least one base profile includes at least one of at leastone base preference or at least one base setting, wherein at least oneof the at least one base preference or at least one base setting areinterpretable into at least one policy rule for at least partiallycontrolling operation of the mobile node including during operation ofthe application.
 20. At least one computer-readable storage mediumhaving computer-readable program code portions stored therein, thecomputer-readable program code portions comprising: a first executableportion for sending a request for an application-specific profile foroperating an application onboard a mobile node, the request includinginformation identifying the application; and a second executable portionfor receiving an application-specific profile in response to therequest, the application-specific profile having been one of created orretrieved based upon the request, wherein the application-specificprofile includes at least one of at least one application-specificpreference or at least one application-specific setting, wherein atleast one of the at least one application-specific preference or atleast one application-specific setting are interpretable into at leastone policy rule for at least partially controlling selection of at leastone of the communication interfaces of the mobile node during operationof the application, and wherein the second executable portion receivesthe application-specific profile such that the application is thereafterconfigurable at least partially based upon the application-specificprofile, the application being at least partially configured based uponthe application-specific profile independent of user input.
 21. At leastone computer-readable storage medium according to claim 20, wherein thefirst executable portion is adapted to send a request including anidentifier associated with the application, and wherein the secondexecutable portion is adapted to receive an application-specific profilehaving been one of created or retrieved at least partially based uponthe identifier.
 22. At least one computer-readable storage mediumaccording to claim 20, wherein the first executable portion is adaptedto send a request including at least one of at least one characteristicor at least one requirement of the application, and wherein the secondexecutable portion is adapted to receive an application-specific profilehaving been one of created or retrieved at least partially based uponthe at least one of the at least one characteristic or the at least onerequirement of the application.
 23. At least one computer-readablestorage medium according to claim 20, wherein the first executableportion is adapted to send a request from the mobile node to a profileserver located remote from the mobile node, and wherein the secondexecutable portion is adapted to receive an application-specific profileat the mobile node from the profile server in response to the request.24. At least one computer-readable storage medium according to claim 20,wherein the second executable portion is adapted to receive theapplication-specific profile such that the application is thereafterconfigurable further based upon at least one base profile, wherein theat least one base profile includes at least one of at least one basepreference or at least one base setting, wherein at least one of the atleast one base preference or at least one base setting are interpretableinto at least one policy rule for at least partially controllingoperation of the mobile node including during operation of theapplication.